<PROJECT NAME>

Requirements Management Plan

The approach we will use for requirements management for the project will be broken down into four areas: requirements identification, requirements analysis, requirements documentation, and ongoing requirements management.

The FNFG project team will facilitate various methods to collect requirements which may include: interviews, focus groups, facilitated workshops, questionnaires, or product prototypes. These will be conducted among the project stakeholders to ensure all requirements are captured.

Documentation: All project documentation will be loaded into the project SharePoint site as the central repository for the project. Appropriate permissions will be granted to the project team for editing and revising documentation.

Requirements Prioritization Process

The business analyst/project manager will facilitate stakeholder meetings in order to establish priorities for all project requirements. This project will use a three-level scale in order to prioritize requirements. The chart below illustrates these levels and defines how requirements will be grouped:

Priority Level	Definition
High (Must Have)	Mission critical. They are required for project success or progression into the next phase.
Medium (Should Have)	Non-core, discretionary functionality that should be deployed but if not ready, deployment would not be delayed.
Low (Nice to Have)	Desirable if time and budget permits.

In Scope / Out of Scope: As the project moves forward, if additional constraints are identified or there are issues with resources, it may be necessary for the project team and stakeholders to meet in order to determine what requirements will be in scope or out of scope.

DELIVERABLES

Deliverable	Description	Reason for exclusion	Stakeholder Initial	Date
SIPOC	High-level picture of the process that depicts how a given process is servicing the customer. It is an acronym for Suppliers - Inputs - Process - Outputs - Customers
Business Requirement	A set of requirements that define what must be delivered to provide value
Current State	Diagram and/or process flow that describes the current state
Future State	Diagram and/or process flow that describes the desired state of the solution
Use Case	Sequence of actions that describes ways in which an actor interacts with a system with the objective of achieving a particular goal
Traceability Matrix	Matrix that is used to ensure that all requirements are met and also used to locate affected system components when there is a requirements change

Note: Reason for exclusion, Stakeholder Initial and Date columns will only be populated in the event that a standard project deliverable is defined as not being needed for a project.